feat: expose exclusion pattern for async-inject-variables
as configuration var
#89
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some variables matching the pattern
org-babel-*
caused some trouble because they had propertized texts for values and thus weren't serializable in a manner that didn't break reading attempts.Since
async-inject-variables
allows for the definition of exclusion patterns, I simply used this to reduce the set of vars that actually get injected into the async process.The default value for the exclusion pattern will drop variables that contain
-overlay
as part of their names since these typically contain overlays which have those propertized texts in my setup.The previous variable
ob-async-inject-variables
has been kept as an alias for backwards compatibility.